Skip to content

[llvm][cmake] Remove version number from runtimes in PROJECTS warnings #152457

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 7, 2025

Conversation

DavidSpickett
Copy link
Collaborator

Judging from the reaction to #152302, we are not ready to make this a fatal error.

Remove the specific version number, and update the libc message to match the others' wording.

Judging from the reaction to llvm#152302
we are not ready to make this a fatal error.

Remove the specific version number, and update the libc message to
match the others' wording.
@DavidSpickett
Copy link
Collaborator Author

I think it makes sense to have this on main as well in case nothing changes in the 22 timeframe, so this PR targets main first and I'll backport if accepted.

Copy link
Contributor

@nikic nikic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@DavidSpickett DavidSpickett merged commit 6cd6de5 into llvm:main Aug 7, 2025
10 checks passed
@DavidSpickett DavidSpickett deleted the llvm-runtime-warning branch August 7, 2025 09:34
@DavidSpickett DavidSpickett added this to the LLVM 21.x Release milestone Aug 7, 2025
@github-project-automation github-project-automation bot moved this to Needs Triage in LLVM Release Status Aug 7, 2025
@DavidSpickett
Copy link
Collaborator Author

/cherry-pick 6cd6de5

@llvmbot
Copy link
Member

llvmbot commented Aug 7, 2025

/pull-request #152470

@llvmbot llvmbot moved this from Needs Triage to Done in LLVM Release Status Aug 7, 2025
tru pushed a commit to llvmbot/llvm-project that referenced this pull request Aug 8, 2025
llvm#152457)

Judging from the reaction to
llvm#152302, we are not ready to
make this a fatal error.

Remove the specific version number, and update the libc message to match
the others' wording.

(cherry picked from commit 6cd6de5)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

4 participants